home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.20000217-20000824
/
000173_news@columbia.edu _Tue Apr 4 18:35:34 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2000-08-23
|
3KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id SAA19823
for <kermit.misc@watsun.cc.columbia.edu>; Tue, 4 Apr 2000 18:35:34 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id SAA11381
for kermit.misc@watsun.cc.columbia.edu; Tue, 4 Apr 2000 18:24:53 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: Steve Manning <manning@execpc.com>
Subject: K95 telnet negotiation help needed
Date: Tue, 04 Apr 2000 17:20:37 -0500
Message-ID: <38ea6ab6$0$56963@news.execpc.com>
Organization: ExecPC Internet - Milwaukee, WI
To: kermit.misc@columbia.edu
(I've experienced this with both v1.1.19 and 1.1.20)
I'm having what I assume to be some growing pains involving the new
telnet negotiation in the latest verisons of K95.
I'm attempting to connect to another system (IBM OS/2) running an
unknown telnet server from my Win95 system.
With version 1.1.17 and earlier, all I had to do with a "vanilla" K95
installation was "set host x.x.x.x", "set terminal type yyy", and
connect.
Since the update to 1.1.19 (and 1.1.20 as well), I've found that if I
follow the steps above, I get the following (with telnet debugging
turned on) as soon as I "set host":
====
[C:\Programs\k95\] K-95> set host 10.210.60.3
Closing connection
Trying 10.210.60.3... (OK)
TELNET SENT WILL AUTHENTICATION
TELNET SENT WILL NAWS
TELNET SENT WILL TERMINAL-TYPE
TELNET SENT WILL NEW-ENVIRONMENT
<wait for outstanding negotiations>
TELNET RCVD WILL SUPPRESS-GO-AHEAD
TELNET SENT DO SUPPRESS-GO-AHEAD
TELNET RCVD WILL ECHO
TELNET SENT DO ECHO
TELNET RCVD DONT ECHO
|TELNET SENT DO LOGOUT
/
?Telnet Protocol Timeout - connection closed
<telnet protocol timeout - connection closed>
[C:\Programs\k95\] K-95>
====
There is a significant pause before the protocol timeout occurs... 30
secs to a minute or so.
I've also found that if I "set telnet wait-for-negotiations off", then
I get right in.
Can someone give me a bit of background here?
I'm worried that I'll need to add the "wait-for-negotiations" setting
to my 400+ .ini files spread around the company if I attempt to deploy
the newer version. (We have a 100-user license.)
Any pointers to info that I've overlooked, or any other info greatly
appreciated.
Steve Manning
Systems Administrator
Mega Marts Inc.
Milwaukee, WI USA
manning@execpc.com